home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Languguage OS 2
/
Languguage OS II Version 10-94 (Knowledge Media)(1994).ISO
/
language
/
embedded
/
mcu332
/
332-101.arc
/
READ.ME
< prev
next >
Wrap
Text File
|
1990-01-22
|
4KB
|
130 lines
EVSbug332 V0.95 (Beta) 12-12-89
1) Shipping List.
This disk should contain the following files:
READ ME This File.
COUGAR CFG EVSbug332 Configuration file.
CONFIG EXE Utility to create Configuration file.
COUGAR EXE EVSbug332 executable file.
PROG-DI EXE Utility to re-program your BCCDI firmware.
BCCDI BIN Support file for PROG-DI.EXE.
BOOT BIN ""
BOOT-DI BIN ""
0 HLP On-line help file for EVSbug332.
1 HLP ""
2 HLP ""
3 HLP ""
4 HLP ""
5 HLP ""
6 HLP ""
7 HLP ""
8 HLP ""
9 HLP ""
A HLP ""
B HLP ""
C HLP ""
D HLP ""
E HLP ""
F HLP ""
G HLP ""
H HLP ""
I HLP ""
J HLP ""
K HLP ""
L HLP ""
HELP MNU ""
ASM TAB Support file for EVSbug332
ASM ERR ""
COMMAND TAB ""
COUGAR DEF Support file for Logitech Mouse.
COUGAR MNU ""
2) Installation
The EVSbug332 monitor should be installed on a hard disk for
best performance; it makes many disk references during a debug
session. Your first step is to create a directory on your hard
disk. Next copy all files from this disk into that directory.
Finally, execute the CONFIG.EXE utility to create (or modify) the
COUGAR.CFG file.
3) Configuration File.
EVSbug332 uses the file, COUGAR.CFG, to customize itself to
your operating environment. EVSbug332 needs to know four parameters
about your system in order to operate correctly.
A) the serial COM port you have connected to the M68332EVS board.
B) the baud speed you wish to use on that port.
C) the DOS path to the directory in which EVSbug332 resides. D)
the DOS path to the directory holding the S-record files to be
downloaded into the M68332EVS.
As shipped, the COUGAR.CFG file is set for COM1:, 9600 Baud,
A:\, and A:\ . You may execute COUGAR.CFG to change any of these
default.
Note: You do **NOT** want to select 1200 baud unless you have
changed the strap on your BCCDI board and unless you are *VERY*
patient. There is a great deal of traffic on the serial lines
between the BCCDI and your PC. Selecting 1200 baud will slow the
monitor system response greatly.
When you have finished configuration, type "COUGAR" to execute
EVSbug332.
4) Re-programming your BCCDI.
Reprogramming of your BCCDI board should be necessary only at
very rare intervals. There are two reasons to reprogram it.
A) Future releases of EVSbug332 may require the firmware in the
BCCDI board to be updated. This should only be necessary when the
major revision number of EVSbug332 is changed.
B) It is also possible, though improbable, that the firmware in
your BCCDI could be corrupted.
Should either occur, you may use the utility PROG-DI.EXE to
re-program the BCCDI firmware. The utility prompts you through the
process.
ERRATA:
1) The Jumber "Jx 1-2" does not exist on your BCCDI board. It
will exist on the next and all future revisions. You must connect
the jumper wire from P2-23 to P2-63.
2) The word "BCCDI" is misspelled as "BBCDI".
5) Rodents.
This disk contains mouse support files for the Logitech Mouse.
The file COUGAR.DEF contains mouse movement definitions. The left
button is defined as "ENTER" and the right button is defined as
"SpaceBar". You may edit this file for other brands of mice. If you
are using a Logitech mouse, remember to load your mouse drivers,
make an entry in your CLICK.SRC file for "COUGAR" and recompile
your "CLICK" file.
Note: Our testing was confined to the Logitech Bus Mouse in several
'286 type machines.
6) Monitor Updates.
Each new release of EVSbug332 with be distributed by the
Motorola MCU Bulletin Board, FREEWARE BBS. I will generate an
archive of all necessary files for each new release. Thus, you will
only have to download one file to receive all of the update. The
FREEWARE BBS is on line 24 hours / day, except for short periods
of maintenance. The FREEWARE BBS phone number is (512) 891-FREE.
You may connect at 300, 1200, or 2400 baud using 8 bits, no Parity,
and 1 Stop bit.
7) Bug Reports.
If you have questions, suggestion for improvement, or Bug
reports, you may contact me through the FREEWARE BBS. Leave E-mail
for the SYSOP. I answer E-mail at least once each business day.
John Dumas